Collaborative public user profile

ABSTRACT

A system to generate a graphical user interface to display a presentation of a set of shared user groups between users of a social networking service is described. Embodiments of the present disclosure relate generally to systems for: receiving an identification of a second user from a user account of a first user; identifying a user group that includes the first user and the second user in response to the identification of the second user from the user account of the first user; retrieving user identifiers of the first user and the second user, wherein the user identifiers may include graphical avatars; generating a group identifier based on the user identifiers; and causing display of a presentation of the user group at a client device.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to graphical userinterfaces (GUI), and more particularly, to systems for generating andcausing display of GUIs.

BACKGROUND

A user profile is a visual display of personal data associated with aspecific user, or a customized desktop environment. A profile referstherefore to the explicit digital representation of a person or entity'sidentity. A profile can be used to store the description of thecharacteristics of a person. This information can be exploited bysystems taking into account the persons' characteristics andpreferences.

Although some people choose to use their real names online, some socialmedia users prefer to be anonymous, identifying themselves by means ofpseudonyms, which reveal varying amounts of personally identifiableinformation.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a networkin accordance with some embodiments, wherein the messaging systemincludes a media collaboration system.

FIG. 2 is block diagram illustrating further details regarding amessaging system, according to example embodiments.

FIG. 3 is a block diagram illustrating various modules of a mediacollaboration system, according to certain example embodiments.

FIG. 4 is an interface diagram depicting a collaborative user profile,according to certain example embodiments.

FIG. 5 is an interface diagram depicting an approval queue, according tocertain example embodiments.

FIG. 6 is an interface diagram depicting a collaborative interface,according to certain example embodiments.

FIG. 7 is an interface diagram depicting a collaborative user profile,according to certain example embodiments.

FIG. 8 is an interface diagram depicting graphical user interfaces togenerate collaborative content, according to certain exampleembodiments.

FIG. 9 is an interface diagram depicting a graphical user interface togenerate collaborative content, according to certain exampleembodiments.

FIG. 10 is a flowchart illustrating a method for managing acollaborative user profile, according to certain example embodiments.

FIG. 11 is a flowchart illustrating a method for managing acollaborative user profile, according to certain example embodiments.

FIG. 12 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described and used to implement variousembodiments.

FIG. 13 is a block diagram illustrating components of a machine,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

A collaborative media system to generate and maintain a collaborativeuser profile is described. Embodiments of the present disclosure relategenerally to systems for: receiving media content from a first useraccount, wherein the media content includes image data, video data, andaudio data, as well as an authentication credential associated with asecond user account; authenticating the media content from the firstuser account based on the authentication credential; presenting themedia content among an approval queue associated with the second useraccount in response to authenticating the media content based on theauthentication credential; receiving an approval of the media contentfrom the second user account; and adding the media content to a mediacollection associated with the second user account, in response to theapproval.

Consider an illustrative example from a user perspective. A user profileis a visual display of personal data associated with a specific user. Asa result of the ubiquity of social networking systems, corporateentities as well as celebrities may desire to maintain an onlinepresence through a user profile. In order to maximize that onlinepresence, the disclosed collaborative media system provides systems andinterfaces for multiple users to collaborate on a single user profile byproviding media content for approval, while the user profile ultimatelyremains under the control of an administrator.

According to certain example embodiments, media content may be generatedby a first user account. For example, a first user account may generatethe media content by providing one or more media items to thecollaborative media system, or by selecting one or more media itemslocated in a shared media repository associated with a second userprofile (i.e., the collaborative user profile). The media items may forexample include images, videos, audio, as well as media filters.

In response to receiving the media content at the collaborative mediasystem, the collaborative media system authenticates the media contentbased on an authentication credential. For example, the first useraccount may provide the authentication credential to the collaborativemedia system. In further embodiments, the collaborative media system mayretrieve the authentication credential from the first user account.

In some embodiments, the collaborative media system assigns a timestampto the media content received from the first user account. The timestampmay for example indicate a time and date in which the media content wascreated by the first user account, or in which the media content wasprovided to the collaborative media system for inclusion in a seconduser account.

The media content may be added to an approval queue associated with thesecond user profile. In some embodiments, a position of the mediacontent within the approval queue may be based on the timestamp. Forexample, a more recent timestamp may result in the media content beingdisplayed more prominently within the approval queue at the beginning,while a later timestamp may result in the media content being displayedtowards the end of the queue. In further embodiments the timestampitself may be presented on a display of the media content within theapproval queue.

In some embodiments, in response to adding the media content to theapproval queue, the collaborative media system may present anotification to the second user account indicating that there is newmedia content to be reviewed for approval. The collaborative mediasystem may receive an approval or a denial of the media content. In thecase of a denial, the media content may be removed from the approvalqueue, and a notification may be presented to the first user accountthat indicates the media content was denied. In the case of an approvalof the media content, in response to receiving the approval, thecollaborative media system adds the media content to a media collectionassociated with the second user account (i.e., the collaborative userprofile).

In some embodiments, the approval of the media content received from thesecond user account may also include one or more updates to the mediacontent. For example, by selecting the media content within the approvalqueue, the second user account may be presented with one or more optionsto modify or alter the media content. The one or more options mayinclude options to add text, alter text, add graphical elements, modifyexisting graphical elements, add audio, modify existing audio, add mediafilters, adjust media filters, adjust colorfulness, chroma, saturation,brightness, contrast, and sharpness of the media content, or alterdisplay attributes of the media content such as a display duration (forephemeral content), geolocation criteria and temporal criteria toreceive access to the media content.

Accordingly, a single collaborative user profile may be maintained by aplurality of users that provide media content to be reviewed by anadministrative account (i.e., the second user profile). The mediacontent can then be presented through second user profile, such that asusers provide requests to view a media collection of the second userprofile, the media content provided by a first user profile may bedisplayed in such a way that it appears to have originated from thesecond user profile.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple client devices 102, each ofwhich hosts a number of applications including a messaging clientapplication 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via a network 106(e.g., the Internet).

Accordingly, each messaging client application 104 is able tocommunicate and exchange data with another messaging client application104 and with the messaging server system 108 via the network 106. Thedata exchanged between messaging client applications 104, and between amessaging client application 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality either within the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, but to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Insome embodiments, this data includes, message content, client deviceinformation, geolocation information, media annotation and overlays,message content persistence conditions, social network information, andlive event information, as examples. In other embodiments, other data isused. Data exchanges within the messaging system 100 are invoked andcontrolled through functions available via GUIs of the messaging clientapplication 104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

Dealing specifically with the Application Program Interface (API) server110, this server receives and transmits message data (e.g., commands andmessage payloads) between the client device 102 and the applicationserver 112. Specifically, the Application Program Interface (API) server110 provides a set of interfaces (e.g., routines and protocols) that canbe called or queried by the messaging client application 104 in order toinvoke functionality of the application server 112. The ApplicationProgram Interface (API) server 110 exposes various functions supportedby the application server 112, including account registration, loginfunctionality, the sending of messages, via the application server 112,from a particular messaging client application 104 to another messagingclient application 104, the sending of media files (e.g., images orvideo) from a messaging client application 104 to the messaging serverapplication 114, and for possible access by another messaging clientapplication 104, the setting of a collection of media data (e.g.,story), the retrieval of a list of friends of a user of a client device102, the retrieval of such collections, the retrieval of messages andcontent, the adding and deletion of friends to a social graph, thelocation of friends within a social graph, opening and application event(e relating to the messaging client application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116, a social network system 122, and a collaborativemedia system 124. The messaging server application 114 implements anumber of message processing technologies and functions, particularlyrelated to the aggregation and other processing of content (e.g.,textual and multimedia content included in messages received frommultiple instances of the messaging client application 104. As will bedescribed in further detail, the text and media content from multiplesources may be aggregated into collections of content (e.g., calledstories, galleries, or collections). These collections are then madeavailable, by the messaging server application 114, to the messagingclient application 104. Other processor and memory intensive processingof data may also be performed server-side by the messaging serverapplication 114, in view of the hardware requirements for suchprocessing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 within thedatabase 120. Examples of functions and services supported by the socialnetwork system 122 include the identification of other users of themessaging system 100 with which a particular user has relationships oris “following,” and also the identification of other entities andinterests of a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message,collection of messages, or graphical element, selectively display andenable access to messages and associated content via the messagingclient application 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., a media collection that includes collectionsof text, image video and audio data). In some examples, a collection ofcontent (e.g., messages, including images, video, text and audio) may beorganized into an “event gallery” or an “event story.” Such a collectionmay be made available for a specified time period, such as the durationof an event to which the content relates. For example, content relatingto a music concert may be made available as a “story” for the durationof that music concert. The collection management system 204 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion of usergenerated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay to the messaging client application104 based on a geolocation of the client device 102. In another example,the annotation system 206 operatively supplies a media overlay to themessaging client application 104 based on other information, such as,social network information of the user of the client device 102. A mediaoverlay may include audio and visual content and visual effects, as wellas augmented reality overlays. Examples of audio and visual contentinclude pictures, texts, logos, animations, and sound effects, as wellas animated facial models, image filters, and augmented reality mediacontent. An example of a visual effect includes color overlaying. Theaudio and visual content or the visual effects can be applied to a mediacontent item (e.g., a photo or video or live stream) at the clientdevice 102. For example, the media overlay including text that can beoverlaid on top of a photograph generated taken by the client device102. In another example, the media overlay includes an identification ofa location overlay (e.g., Venice beach), a name of a live event, or aname of a merchant overlay (e.g., Beach Coffee House). In anotherexample, the annotation system 206 uses the geolocation of the clientdevice 102 to identify a media overlay that includes the name of amerchant at the geolocation of the client device 102. The media overlaymay include other indicia associated with the merchant. The mediaoverlays may be stored in the database 120 and accessed through thedatabase server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay should be offered to other users. Theannotation system 206 generates a media overlay that includes theuploaded content and associates the uploaded content with the selectedgeolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation. For example, theannotation system 206 associates the media overlay of a highest biddingmerchant with a corresponding geolocation for a predefined amount oftime

FIG. 3 is a block diagram illustrating components of the collaborativemedia system 124 that configure the collaborative media system 124 toperform operations that include receiving media content from a firstuser account, wherein the media content includes image data, video data,and audio data, as well as an authentication credential associated witha second user account; authenticating the media content from the firstuser account based on the authentication credential; presenting themedia content among an approval queue associated with the second useraccount in response to authenticating the media content based on theauthentication credential; receiving an approval of the media contentfrom the second user account; and adding the media content to a mediacollection associated with the second user account, in response to theapproval, according to certain example embodiments.

The collaborative media system 124 is shown as including a presentationmodule 302, a user profile module 304, a media module 306, and acommunication module 308, all configured to communicate with each other(e.g., via a bus, shared memory, or a switch). Any one or more of thesemodules may be implemented using one or more processors 310 (e.g., byconfiguring such one or more processors to perform functions describedfor that module) and hence may include one or more of the processors310.

Any one or more of the modules described may be implemented usinghardware alone (e.g., one or more of the processors 310 of a machine) ora combination of hardware and software. For example, any moduledescribed of the collaborative media system 124 may physically includean arrangement of one or more of the processors 310 (e.g., a subset ofor among the one or more processors of the machine) configured toperform the operations described herein for that module. As anotherexample, any module of the collaborative media system 124 may includesoftware, hardware, or both, that configure an arrangement of one ormore processors 310 (e.g., among the one or more processors of themachine) to perform the operations described herein for that module.Accordingly, different modules of the collaborative media system 124 mayinclude and configure different arrangements of such processors 310 or asingle arrangement of such processors 310 at different points in time.Moreover, any two or more modules of the collaborative media system 124may be combined into a single module, and the functions described hereinfor a single module may be subdivided among multiple modules.Furthermore, according to various example embodiments, modules describedherein as being implemented within a single machine, database, or devicemay be distributed across multiple machines, databases, or devices.

FIG. 4 is an interface diagram 400 depicting a collaborative userprofile 405 displayed at a client device 102, according to certainexample embodiments. As seen in FIG. 4, the collaborative user profile405 comprises a display of a media collection 410 that includes a set ofmedia content such as media content 415. As discussed herein, the mediacontent comprising the media collection 410 may be originated from aplurality of user accounts, and approved for display within the mediacollection 410 by an administrator of the user account 420.

The administrator of the user account 420 may additionally provideinputs to define a position of the media content 415 within the mediacollection 410. For example, upon review and approval of the mediacontent 415 from an approval queue (such as the approval queue 505depicted in FIG. 5), the administrator of the user account 420 mayprovide an input defining the position of the media content 415 withinthe media collection 410. In some embodiments, the input may includegrabbing and dragging the media content 415 to the desired positionamong the media collection 410, while in further embodiments, the inputmay include an input that assigns special status to the media content415 (for example, defining the media content 415 as a highlight). Ineven further embodiments, the position of the media content 415 maysimply be based on when the media content 415 was approved for displaywithin the media collection 410, with the most recent additions beingdisplayed at a first position among the media collection 410.

FIG. 5 is an interface diagram 500 depicting an approval queue 505,according to certain example embodiments. As seen in FIG. 5, theapproval queue 505 comprises media content such as the media, content510. A position of the media content within the approval queue 505 maybe based on a timestamp, such as the timestamp 515.

For example, the media content 510 may be generated by a first useraccount and submitted to the collaborative media system 124 for reviewby an administrator of a second user account. The administrator of thesecond user account may then be presented with the approval queue 505,in order to provide one or more inputs selecting media content, such asthe media content 510. The selected media content may then be approved,modified, or denied.

FIG. 6 is an interface diagram 600 depicting a collaborative interface605, according to certain example embodiments. As seen in FIG. 6, thecollaborative interface 605 may include an interface to display mediastatistics 615 of media content comprising a media collection, such asthe media content 415 depicted in FIG. 4.

In some embodiments, the media statistics 615 may only be made availableto an administrator of the collaborative profile, while in furtherembodiments the media statistics 615 may be made available to users withauthentication credentials for the collaborative user profile.

In some embodiments, the collaborative interface 605 may be presented inresponse to receiving an input that selects media content, such as themedia content 415, from an administrator of the collaborative userprofile, or a user with authentication credentials for the collaborativeuser profile. In such embodiments, the media statistics 615 wouldcorrespond with the selected media content. For example, a qualifieduser may provide a tactile input that includes input attributes such asa pressure or duration, and in response to the collaborative mediasystem 124 detecting the input attribute transgressing a Threshold value(e.g., a threshold duration, a threshold pressure), the collaborativemedia system may generate and cause display of the collaborativeinterface 605.

In some embodiments, a user presented with the collaborative interface605 may provide an input to identify a location 610 associated with themedia statistics 615. By defining the location 610, the collaborativemedia system 124 may retrieve media statistics 615 associated with theidentified media content (e.g., media content 415), based on thelocation 610. Thus, the media statistics 615 may provide an indicationof regional statistics of the identified media content.

In some embodiments, the collaborative interface 620 may furthercomprise a display of media content 620, wherein the media content 620is curated from the media collection of the identified media content(e.g., media content 415 corresponds to media collection 410). A userpresented with the collaborative interface 605 may provide an inputselecting media content from among the media content 620, and inresponse the collaborative media system 124 may cause display ofcorresponding media statistics 615.

FIG. 7 is an interface diagram 700 depicting a collaborative userprofile 705, according to certain example embodiments. As seen in FIG.7, the collaborative user profile 705 includes a display of prominentcontent 710 at a position within the collaborative user profile 705 thatis separate from the display of the media collection 715.

In some embodiments, an administrator of the collaborative user profile705 may provide an approval of media content from among media contentdisplayed within the approval queue (e.g., the approval queue 505depicted in FIG. 5), wherein the approval of the media content (e.g.,the prominent content 710) includes an administration of a specialstatus to the media content that defines presentation features for themedia content. For example, the administrator may provide an input todefine media content as “prominent content,” and in response, thecollaborative media system 124 may present the media content at aposition within the collaborative user profile separate from the mediacollection 715 (i.e., the prominent content 710).

FIG. 8 is an interface diagram 800 depicting graphical user interfaces(GUIs) 805, 810, and 815 to generate collaborative content 820,according to certain example embodiments.

As seen in FIG. 8, the GUI 805 comprises a display of a collection ofmedia items 820. In some embodiments, the GUI 805 may be displayed at acollaborative user's client device (e.g., client device 102). Thecollection of media items 820 may either reside locally on the clientdevice 102, or in some embodiments may comprise a shared mediarepository located within the database 120, and that may be accessibleby all collaborative users (e.g., users with authentication credentialsassociated with the collaborative user profile).

In response to receiving a selection of a media item (e.g., the mediaitem 825) from among the collection of media items 820, thecollaborative media system 124 may cause display of the GUI 810 togenerate media content (e.g., the media content 830). For example, auser may provide one or more inputs to add text or graphical elements tothe media item 825.

In response to generating the media content 830, the collaborative mediasystem 124 may cause display of the GUI 815 to display the media content830, and to add a caption or title to the media content 830. In someembodiments, selecting the graphical icon 835 may cause thecollaborative media system 124 to add the media content 830 to theapproval queue 505 depicted in FIG. 5.

FIG. 9 is an interface diagram 900 depicting a graphical user interface905 to generate collaborative content 910, according to certain exampleembodiments.

As seen in FIG. 9, a collaborative user may generate media content 910,and add the media content to a media collection (e.g., the mediacollection 920) by providing an input that selects the graphical icon915. For example, the graphical icon 915 may be displayed on the mediacontent 910 in response to the collaborative media system 124determining that the collaborative user has the authenticationcredentials required for a collaborative user profile.

The collaborative user may select a media collection, such as the mediacollection 920, and in response the collaborative media system 124 mayadd the media content 910 to the media collection 920.

FIG. 10 is a flowchart illustrating a method 1000 for maintaining andmanaging a collaborative user profile, according to certain exampleembodiments. Operations of the method 1000 may be performed by themodules described above with respect to FIG. 3. As shown in FIG. 10, themethod 1000 includes one or more operations 1002, 1004, 1006, 1008, and1010.

At operation 1002, the media module 306 receives media content from afirst user account, wherein the media content comprises media data andan authentication credential. For example, the first user account may beassociated with a collaborative user account (e.g., a second useaccount), and the authentication credential may be associated with acollaborative user profile. The media content received by the mediamodule 306 may include the media content 415 depicted in FIG. 4, as wellas the media content 510 in the approval queue 505 of FIG. 5. In someembodiments, the collaborative user account (e.g., the second useraccount) may be associated with a client device. A seconduser/administrator of the collaborative user account may receive themedia content at a client device 102.

At operation 1004, the user profile module 304 authenticates the firstuser account based on the authentication credential. For example, theauthentication credential may be provided by the first user account tothe user profile module 304, or in some embodiments, the user profilemodule 304 may maintain a list of authorized user profiles, which may bedefined by an administrator of a collaborative profile. In someembodiments, the authentication may be performed by the client device102 (e.g., the client device associated with the administrator of thecollaborative user account). For example, the administrator may retainand save authentication criteria associated with the collaborative useraccount at the client device 102.

At operation 1006, in response to authenticating the first user accountbased on the authentication credential, the presentation module 302presents the media content among an approval queue, such as the approvalqueue 505 depicted in FIG. 5. As discussed above, the approval queue maybe associated with a second user profile (i.e., a collaborative userprofile).

In some embodiments, the media module 306 may assign a timestamp to themedia content in response to the user profile module 304 authenticatingthe first user account, wherein the timestamp indicates a time and datein which the media content was received by the media module 306, or insome embodiments, a time and date in which the media content was createdby the first user account. The presentation module 302 may present themedia content at a position within the approval queue based on thetimestamp.

At operation 1008, the media module 306 receives an approval of themedia content from a second user account associated with thecollaborative user profile. For example, the second user account may bean administrator associated with the collaborative user profile.

In some embodiments, the approval of the media content received from thesecond user account may additionally include presentation instructionsthat define a position among a media collection to display the mediacontent.

At operation 1010, in response to receiving the approval of the mediacontent from the second user account, the presentation module adds themedia content to a media collection associated with the second useraccount. A position of the media content among the media collection maybe based on inputs received from the second user account.

FIG. 11 is a flowchart illustrating a method 1100 for maintaining andmanaging a collaborative user profile, according to certain exampleembodiments. Operations of the method 1100 may be performed by themodules described above with respect to FIG. 3. As shown in FIG. 11, themethod 1100 includes one or more operations 1102, and 1104.

At operation 1102, the communication module 308 receives a request toview a media collection associated with a second user account from athird user account. For example, the second user account may be acollaborative user profile, and the third user account may be a publicuser of a social network system, or a social network connection of thesecond user account.

In response to receiving the request to view the media collectionassociated with the second user account, the presentation module 302causes display of at least the media content received from the firstuser account (i.e., a collaborative user associated with thecollaborative user profile) to the third user account. The display ofthe media content to the third user account may be presented such thatit appears that the media content originated from the second useraccount, and that there is no indication that the media content wasgenerated by a separate user account.

Software Architecture

FIG. 12 is a block diagram illustrating an example software architecture1206, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 12 is a non-limiting example of asoftware architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 1206 may execute on hardwaresuch as the machine 1300 of FIG. 13 that includes, among other things,processors 1304, memory 1314, and I/O components 1318. A representativehardware layer 1252 is illustrated and can represent, for example, themachine 1200 of FIG. 12. The representative hardware layer 1252 includesa processing unit 1254 having associated executable instructions 1204.Executable instructions 1204 represent the executable instructions of hesoftware architecture 1206, including implementation of the methods,components and so forth described herein. The hardware layer 1252 alsoincludes memory and/or storage modules memory/storage 1256, which alsohave executable instructions 1204. The hardware layer 1252 may alsocomprise other hardware 1258.

In the example architecture of FIG. 12, the software architecture 1206may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1206may include layers such as an operating system 1202, libraries 1220,applications 1216 and a presentation layer 1214. Operationally, theapplications 1216 and/or other components within the layers may invokeapplication programming interface (API) API calls 1208 through thesoftware stack and receive a response as in response to the API calls1208. The layers illustrated are representative in nature and not allsoftware architectures have all layers. For example, some mobile orspecial purpose operating systems may not provide aframeworks/middleware 1218, while others may provide such a layer. Othersoftware architectures may include additional or different layers.

The operating system 1202 may manage hardware resources and providecommon services. The operating system 1202 may include, for example, akernel 1222, services 1224 and drivers 1226. The kernel 1222 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1222 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1224 may provideother common services for the other software layers. The drivers 1226are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1226 include display drivers, cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 1220 provide a common infrastructure that is used by theapplications 1216 and/or other components and/or layers. The libraries1220 provide functionality that allows other software components toperform tasks in an easier fashion than to interface directly with theunderlying operating system 1202 functionality (e.g., kernel 1222,services 1224 and/or drivers 1226). The libraries 1220 may includesystem libraries 1244 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 1220 may include API libraries 1246 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphicslibraries (e.g., an OpenGL framework that may be used to render 2D and3D in a graphic content on a display), database libraries (e.g., SQLitethat may provide various relational database functions), web libraries(e.g., WebKit that may provide web browsing functionality), and thelike. The libraries 1220 may also include a wide variety of otherlibraries 1248 to provide many other APIs to the applications 1216 andother software components/modules.

The frameworks/middleware 1218 (also sometimes referred to asmiddleware) provide a higher-level common infrastructure that may beused by the applications 1216 and/or other software components/modules.For example, the frameworks/middleware 1218 may provide various graphicuser interface (GUI) functions, high-level resource management,high-level location services, and so forth. The frameworks/middleware1218 may provide a broad spectrum of other APIs that may be utilized bythe applications 1216 and/or other software components/modules, some ofwhich may be specific to a particular operating system 1202 or platform.

The applications 1216 include built-in applications 1238 and/orthird-party applications 1240. Examples of representative built-inapplications 1238 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third-party applications 1240 may include anapplication developed using the ANDROID™ or OS™ software development kit(SDK) by an entity other than the vendor of the particular platform, andmay be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 1240 may invoke the API calls 1208 provided bythe mobile operating system (such as operating system 1202) tofacilitate functionality described herein.

The applications 1216 may use built in operating system functions (e.g.,kernel 1222, services 1224 and/or drivers 1226), libraries 1220, andframeworks/middleware 1218 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such aspresentation layer 1214. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 13 is a block diagram illustrating components of a machine 1300,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 13 shows a diagrammatic representation of the machine1300 in the example form of a computer system, within which instructions1310 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1300 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 1310 may be used to implement modules or componentsdescribed herein. The instructions 1310 transform the general,non-programmed machine 1300 into a particular machine 1300 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1300 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1300 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1300 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 1310, sequentially or otherwise, that specify actions to betaken by machine 1300. Further, while only a single machine 1300 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 1310 to perform any one or more of the methodologiesdiscussed herein.

The machine 1300 may include processors 1304, memory memory/storage1306, and I/O components 1318, which may be configured to communicatewith each other such as via a bus 1302. The memory/storage 1306 mayinclude a memory 1314, such as a main memory, or other memory storage,and a storage unit 1316, both accessible to the processors 1304 such asvia the bus 1302. The storage unit 1316 and memory 1314 store theinstructions 1310 embodying any one or more of the methodologies orfunctions described herein. The instructions 1310 may also reside,completely or partially, within the memory 1314, within the storage unit1316, within at least one of the processors 1304 (e.g., within theprocessor's cache memory), or any suitable combination thereof, duringexecution thereof by the machine 1300. Accordingly, the memory 1314, thestorage unit 1316, and the memory of processors 1304 are examples ofmachine-readable media.

The I/O components 1318 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1318 that are included in a particular machine 1300 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 1318 may include many other components that are not shown inFIG. 13. The I/O components 1318 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the I/O components 1318may include output components 1326 and input components 1328. The outputcomponents 1326 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1328 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1318 may includebiometric components 1330, motion components 1334, environmentalenvironment components 1336, or position components 1338 among a widearray of other components. For example, the biometric components 1330may include components to detect expressions hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1334 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environment components 1336 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1338 mayinclude location sensor components (e.g., a Global Position system (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1318 may include communication components 1340operable to couple the machine 1300 to a network 1332 or devices 1320via coupling 1322 and coupling 1324 respectively. For example, thecommunication components 1340 may include a network interface componentor other suitable device to interface with the network 1332. In furtherexamples, communication components 1340 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1320 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 1340 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1340 may include Radio Frequency Identification(RHD) tag reader components, NFC smart tag detection components, opticalreader components (e.g., an optical sensor to detect one-dimensional barcodes such as Universal Product Code (UPC) bar code, multi-dimensionalbar codes such as Quick Response (QR) code, Aztec code, Data Matrix,Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and otheroptical codes), or acoustic detection components (e.g., microphones toidentify tagged audio signals). In addition, a variety of informationmay be derived via the communication components 1340, such as, locationvia Internet Protocol (IP) geo-location, location via Wi-Fi® signaltriangulation, location via detecting a NFC beacon signal that mayindicate a particular location, and so forth.

Glossary

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine, and includes digital or analog communications signals orother intangible medium to facilitate communication of suchinstructions. Instructions may be transmitted or received over thenetwork using a transmission medium via a network interface device andusing any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smart phones, tablets, ultra books, netbooks,laptops, multi-processor systems, microprocessor-based or programmableconsumer electronics, game consoles, set-top boxes, or any othercommunication device that a user may use to access a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network may include a wireless or cellular network andthe coupling may be a Code Division Multiple Access (CDMA) connection, aGlobal System for Mobile communications (GSM) connection, or other typeof cellular or wireless coupling. In this example, the coupling mayimplement any of a variety of types of data transfer technology, such asSingle Carrier Radio Transmission Technology (1×RTT), Evolution-DataOptimized (EVDO) technology, General Packet Radio Service (GPRS)technology, Enhanced Data rates for GSM Evolution (EDGE) technology,third Generation Partnership Project (3GPP) including 3G, fourthgeneration wireless (4G) networks, Universal Mobile TelecommunicationsSystem (UMTS), High Speed Packet Access (HSPA), WorldwideInteroperability for Microwave Access (WiMAX), Long Term Evolution (LTE)standard, others defined by various standard setting organizations,other long range protocols, or other data transfer technology.

“EMPHEMERAL MESSAGE” in this context refers to a message that isaccessible for a time-limited duration. An ephemeral message may be atext, an image, a video and the like. The access time for the ephemeralmessage may be set by the message sender. Alternatively, the access timemay be a default setting or a setting specified by the recipient.Regardless of the setting technique, the message is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, deviceor other tangible media able to store instructions and data temporarilyor permanently and may include, but is not be limited to, random-accessmemory (RAM), read--only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, physical entity or logichaving boundaries defined by function or subroutine calls, branchpoints, application program interfaces (APIs), or other technologiesthat provide for the partitioning or modularization of particularprocessing or control functions. Components may be combined via theirinterfaces with other components to carry out a machine process. Acomponent may be a packaged functional hardware unit designed for usewith other components and a part of a program that usually performs aparticular function of related functions. Components may constituteeither software components (e.g., code embodied on a machine-readablemedium) or hardware components. A “hardware component” is a tangibleunit capable of performing certain operations and may be configured orarranged in a certain physical manner. In various example embodiments,one or more computer systems a standalone computer system, a clientcomputer system, or a server computer system) or one or more hardwarecomponents of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a Field-Programmable Gate Array (FPGA) or an ApplicationSpecific Integrated Circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component”(or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)). The performance of certain of the operations may bedistributed among the processors, not only residing within a singlemachine, but deployed across a number of machines. In some exampleembodiments, the processors or processor-implemented components may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the processors or processor-implemented components may bedistributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands”, “op codes”, “machine code”, etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a Central Processing Unit (CPU), aReduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an Application Specificintegrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC)or any combination thereof. A processor may further be a multi-coreprocessor having two or more independent processors (sometimes referredto as “cores”) that may execute instructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred, forexample giving date and time of day, sometimes accurate to a smallfraction of a second.

What is claimed is:
 1. A method comprising: receiving, at a client device, media content from a first user account, the media content comprising media data and a credential; authenticating the media content at the client device based on the credential; presenting the media content among an approval queue associated with a second user account at the client device, in response to the authenticating the media content based on the credential; receiving an approval of the media content from the second user account; and adding the media content to a media collection associated with the second user account in response to the receiving the approval of the media content.
 2. The method of claim 1, wherein second user account includes a plurality of media collections that include the media collection, and the receiving the approval of the media content from the second user account includes: receiving an identification of the media collection.
 3. The method of claim 1, wherein the presenting the media content among the approval queue associated with the second user account includes: applying a timestamp to the media content in response to the receiving the media content from the first user account; and presenting the media content among the approval queue based on the timestamp.
 4. The method of claim 1, wherein the method further comprises: receiving a request to view the media collection associated with the second user account from a third user account; and presenting the media content received from the first user account to the third user account, in response to the request to view the media collection associated with the second user account.
 5. The method of claim 1, wherein the receiving the media content from the first user account further comprises: receiving a request to access a media repository associated with the second user account from the first user account, the media repository comprising a plurality of media items; receiving a selection of a media item from among the plurality of media items from the first user account; and generating the media content based on the media item.
 6. The method of claim 1, wherein the receiving the approval of the media content from the second user account includes: receiving an update to the media content from the second user account; updating the media content based on the update; and adding the updated media content to the media collection associated with the second user account.
 7. The method of claim 1, wherein the method further comprises: presenting a notification to the second user account in response to the presenting the media content among the approval queue associated with the second user account.
 8. The method of claim 1, wherein the media data includes one or more of a list that comprises: image data; video data; and audio data.
 9. A system comprising: a memory; and at least one hardware processor coupled to the memory and comprising instructions that causes the system to perform operations comprising: receiving, at a client device, media content from a first user account, the media content comprising media data and a credential; authenticating the media content at the client device based on the credential; presenting the media content among an approval queue associated with a second user account at the client device in response to the authenticating the media content based on the credential; receiving an approval of the media content from the second user account; and adding the media content to a media collection associated with the second user account in response to the receiving the approval of the media content.
 10. The system of claim 9, wherein second user account includes a plurality of media collections that include the media collection, and the receiving the approval of the media content from the second user account includes: receiving an identification of the media collection.
 11. The system of claim 9, wherein the presenting the media content among the approval queue associated with the second user account includes: applying a timestamp to the media content in response to the receiving the media content from the first user account; and presenting the media content among the approval queue based on the timestamp.
 12. The system of claim 9, wherein the instructions cause the system to perform operations further comprising: receiving a request to view the media collection associated with the second user account from a third user account; and presenting the media content received from the first user account to the third user account, in response to the request to view the media collection associated with the second user account.
 13. The system of claim 9, wherein the receiving the media content from the first user account further comprises: receiving a request to access a media repository associated with the second user account from the first user account, the media repository comprising a plurality of media items; receiving a selection of a media item from among the plurality of media items from the first user account; and generating the media content based on the media item.
 14. The system of claim 9, wherein the receiving the approval of the media content from the second user account includes: receiving an update to the media content from the second user account; updating the media content based on the update; and adding the updated media content to the media collection associated with the second user account.
 15. The system of claim 9, wherein the instructions cause the system to perform operations further comprising: presenting a notification to the second user account in response to the presenting the media content among the approval queue associated with the second user account.
 16. The system of claim 9, wherein the media data includes one or more of a list that comprises: image data; video data; and audio data.
 17. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising: receiving, at a client device, media content from a first user account, the media content comprising media data and a credential; authenticating the media content at the client device based on the credential; presenting the media content among an approval queue associated with a second user account in response to the authenticating the media content based on the credential; receiving an approval of the media content from the second user account; and adding the media content to a media collection associated with the second user account in response to the receiving the approval of the media content.
 18. The non-transitory machine-readable storage medium of claim 17, wherein second user account includes a plurality of media collections that include the media collection, and the receiving the approval of the media content from the second user account includes: receiving an identification of the media collection.
 19. The non-transitory machine-readable storage medium of claim 17, wherein the presenting the media content among the approval queue associated with the second user account includes: applying a timestamp to the media content in response to the receiving the media content from the first user account; and presenting the media content among the approval queue based on the timestamp.
 20. The non--transitory machine-readable storage medium of claim 17, wherein the receiving the media content from the first user account further comprises: receiving a request to access a media repository associated with the second user account from the first user account, the media repository comprising a plurality of media items; receiving a selection of a media item from among the plurality of media items from the first user account; and generating the media content based on the media item. 